home *** CD-ROM | disk | FTP | other *** search
-
-
-
- HHHH2222PPPPHHHH((((1111)))) 22223333////OOOOcccctttt////99998888 ((((ppppeeeerrrrllll 5555....000000005555,,,, ppppaaaattttcccchhhh 00002222)))) HHHH2222PPPPHHHH((((1111))))
-
-
-
- NNNNAAAAMMMMEEEE
- h2ph - convert .h C header files to .ph Perl header files
-
- SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
- hhhh2222pppphhhh [[[[----dddd ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn ddddiiiirrrreeeeccccttttoooorrrryyyy]]]] [[[[----rrrr |||| ----aaaa]]]] [[[[----llll]]]] [[[[hhhheeeeaaaaddddeeeerrrrffffiiiilllleeeessss]]]]
-
- DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
- _h_2_p_h converts any C header files specified to the
- corresponding Perl header file format. It is most easily
- run while in /usr/include:
-
- cd /usr/include; h2ph * sys/*
-
- or
-
- cd /usr/include; h2ph -r -l .
-
- The output files are placed in the hierarchy rooted at
- Perl's architecture dependent library directory. You can
- specify a different hierarchy with a ----dddd switch.
-
- If run with no arguments, filters standard input to standard
- output.
-
- OOOOPPPPTTTTIIIIOOOONNNNSSSS
- -d destination_dir
- Put the resulting ....pppphhhh files beneath ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn____ddddiiiirrrr,
- instead of beneath the default Perl library location
- ($Config{'installsitsearch'}).
-
- -r Run recursively; if any of hhhheeeeaaaaddddeeeerrrrffffiiiilllleeeessss are directories,
- then run _h_2_p_h on all files in those directories (and
- their subdirectories, etc.). ----rrrr and ----aaaa are mutually
- exclusive.
-
- -a Run automagically; convert hhhheeeeaaaaddddeeeerrrrffffiiiilllleeeessss, as well as any
- ....hhhh files which they include. This option will search
- for ....hhhh files in all directories which your C compiler
- ordinarily uses. ----aaaa and ----rrrr are mutually exclusive.
-
- -l Symbolic links will be replicated in the destination
- directory. If ----llll is not specified, then links are
- skipped over.
-
- -h Put ``hints'' in the .ph files which will help in
- locating problems with _h_2_p_h. In those cases when you
- rrrreeeeqqqquuuuiiiirrrreeee a ....pppphhhh file containing syntax errors, instead of
- the cryptic
-
- [ some error condition ] at (eval mmm) line nnn
-
- you will see the slightly more helpful
-
-
-
- Page 1 (printed 10/23/98)
-
-
-
-
-
-
- HHHH2222PPPPHHHH((((1111)))) 22223333////OOOOcccctttt////99998888 ((((ppppeeeerrrrllll 5555....000000005555,,,, ppppaaaattttcccchhhh 00002222)))) HHHH2222PPPPHHHH((((1111))))
-
-
-
- [ some error condition ] at filename.ph line nnn
-
- However, the ....pppphhhh files almost double in size when built
- using ----hhhh.
-
- -D Include the code from the ....hhhh file as a comment in the
- ....pppphhhh file. This is primarily used for debugging _h_2_p_h.
-
- EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT
- No environment variables are used.
-
- FFFFIIIILLLLEEEESSSS
- /usr/include/*.h
- /usr/include/sys/*.h
-
- etc.
-
- AAAAUUUUTTTTHHHHOOOORRRR
- Larry Wall
-
- SSSSEEEEEEEE AAAALLLLSSSSOOOO
- _p_e_r_l(1)
-
- DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
- The usual warnings if it can't read or write the files
- involved.
-
- BBBBUUUUGGGGSSSS
- Doesn't construct the %sizeof array for you.
-
- It doesn't handle all C constructs, but it does attempt to
- isolate definitions inside evals so that you can get at the
- definitions that it can translate.
-
- It's only intended as a rough tool. You may need to dicker
- with the files produced.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 2 (printed 10/23/98)
-
-
-
-
-
-
- HHHH2222PPPPHHHH((((1111)))) 22223333////OOOOcccctttt////99998888 ((((ppppeeeerrrrllll 5555....000000005555,,,, ppppaaaattttcccchhhh 00002222)))) HHHH2222PPPPHHHH((((1111))))
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Page 3 (printed 10/23/98)
-
-
-
-
-
-
-